Media Platform of the Innovatics Pioneer

As the capabilities and service levels of enterprise database systems have evolved, they have collided with incumbent technologies such as TP-Monitors or Message Oriented Middleware (MOM). Webelieve this trend will continue and have architected the upcoming release of SQL Server to advance thistechnology trend. This paper describes the Service Oriented Database Architecture (SODA) developedfor the Microsoft SQL Server DBMS. First, it motivates the need for building Service OrientedArchitecture (SOA) features directly into a database engine. Second, it describes a set of features in SQLServer that have been designed for SOA use. Finally, it concludes with some thoughts on how SODAcan enable multiple service deployment topologies. INTRODUCTIONThree to five years ago, the SQL Server architects saw large scale loosely coupled system architecturesemerging as a natural pattern; particularly in Internet scale transaction processing systems. We observeda natural evolutionary pattern as many of these large systems ran into scaling and availability issues withtheir first and second generation architectures that were often built on tightly coupled, large scaleplatforms with monolithic, and sometimes clustered, databases at their core. Many of these successfulsystems are now based upon a loosely coupled, service centric, architecture. With loose coupling andservice based partitioning, large systems exhibit more resilience to failure and resources may be addedincrementally throughout the architecture as needs change. This presents a new set of challenges toenterprise database systems supporting these scenarios. Observing this shift, the SQL Server team responded by adding a number of specific features to SQLServer to address the needs of Service Oriented Architectures. Collectively, these features implementwhat we refer to as a Service Oriented Database Architecture. We believe many of the featuresassociated with SODA will ultimately become as commonplace in database systems as networkcommunications, thread pooling, and stored procedure logic have become. In this talk, we describe the architecture behind four of the SOA features available in the upcomingrelease of SQL Server: • SQLCLR: Embedding the Common Language Runtime (CLR) in the core databaseengine. Deep integration is the key to success; a hosting layer between the SQL engine andthe CLR allows resources, such as memory and threads, to be coordinated between theruntime and database engine. System or user developed assemblies are stored and loadeddirectly from the database rather than the file system reducing administrative complexity. A